Repository navigation
refactor: no site names in the builder script, docs or fixtures - #54
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
run-on-builder.shno longer defaults to one build machine or a fixed personal checkout path.EB_STACK_BUILDERis now required. WhenEB_STACK_BINis unset, the script uses the checkout at the same path under the builder's$HOME.Help, docs, skills and fixtures use a neutral example site and EESSI target names (
zen2.list,zen4.list,$SCRATCH,x86_64/amd/zen4), and a CI step fails on site names in the tree. Program behaviour doesn't change.The EESSI bot inventory still names
eessi-bot-surf, because that is EESSI's own data and a flag overrides it.Migration: set
EB_STACK_BUILDERto the build machine, and setEB_STACK_BINtoo if the two checkouts live in different places.